Forensic Event Verification Report
No event with ID {{ event_id }} exists in the database.
This report verifies whether the database record for this event has been altered since it was originally logged. When SecureGPS ingests a GPS event, it creates an HMAC-SHA256 cryptographic signature of the record's key fields (device ID, timestamp, coordinates, and detection decision) and stores it alongside the event.
To verify integrity, we recompute the signature from the current database values and compare it to the original. If someone edits the database directly — to change a CHALLENGE to an ALLOW, for example — the signatures will no longer match.
This event was flagged as CHALLENGE by the detection engine, meaning the GPS data exhibited characteristics consistent with spoofing: {{ event.notes }}.
{% if verified %} The VERIFIED status confirms that this detection record is authentic and unmodified — it has not been tampered with after the fact. This is important for forensic evidence: the alert is genuine and can be trusted as an accurate record of what the system detected at the time of ingestion. {% else %} The TAMPERED status means this record has been modified after ingestion. The detection decision or event details may have been altered, making this record unreliable as forensic evidence. {% endif %}
This event was classified as ALLOW — the GPS data passed all detection checks (speed, geofence, signal quality, bearing) and showed no signs of spoofing.
{% if verified %} The VERIFIED status confirms this classification is authentic and unmodified. No one has retroactively changed the detection result in the database. {% else %} The TAMPERED status means this record has been modified after ingestion. It is possible the original detection decision was different, making this record unreliable. {% endif %}